Creating a search index within a data storage library

ABSTRACT

A computer-implemented method according to one embodiment includes initiating a creation of a search index for a data storage cartridge, transparently loading the data storage cartridge into a data storage drive of a data storage library, creating the search index, utilizing the data storage cartridge and the data storage drive, and storing the search index.

BACKGROUND

The present invention relates to data storage systems, and more specifically, this invention relates to creating a search index for data located on data storage cartridges.

Automated data storage libraries are known for providing cost effective storage and retrieval of large quantities of data. The data in automated data storage libraries is typically stored on media of data storage cartridges that are, in turn, stored at storage slots or the like inside the library in a fashion that renders the media, and its resident data, accessible for physical retrieval. Such data storage cartridges are commonly termed “removable media.” Data storage cartridge media may comprise any type of media on which data may be stored and which may serve as removable media, including but not limited to magnetic media (such as magnetic tape or disks), optical media (such as optical tape or discs), electronic media (such as PROM, EEPROM, flash PROM, CompactFlash™, Smartmedia™, Memory Stick™, etc.), or other suitable media. An example of a data storage cartridge that is widely employed in automated data storage libraries for mass data storage is a magnetic tape cartridge.

In addition to data storage media, automated data storage libraries typically comprise data storage drives that store data to, and/or retrieve data from, the data storage cartridge media. Further, automated data storage libraries typically comprise I/O stations at which data storage cartridges are supplied or added to, or removed from, the library. The transport of data storage cartridges between data storage slots, data storage drives, and I/O stations is typically accomplished by one or more accessors. Such accessors have grippers for physically retrieving the selected data storage cartridges from the storage slots within the automated data storage library and transporting such cartridges to the data storage drives by moving, for example, in the horizontal (X) and vertical (Y) directions.

In an effort to increase storage capacity, deep slot technology allows for storage cells that contain more than a single data storage cartridge. Such storage libraries allow for higher density, or more cartridges stored per square foot. In ‘deep slot’ libraries, two or more cartridges may be stored in a multi-cartridge deep slot cell, arrayed in series, one behind the other, in tiers ranging from a frontmost tier to a rearmost tier.

Additionally, it may be desirable to perform a search on stored data. However, currently, when it comes to searching data stored on removable media, a host application and one or more servers retrieve data from a data storage library and perform the search of the retrieved data by the host application at the one or more servers. This is very resource intensive and includes the writing of scripts (to manage the load, read, search, and search results), server usage, device driver usage, host application usage, and communication path usage, decompression, decryption, etc. Further, searching large amounts of stored data within a storage library can be very time consuming.

What is needed is a way to perform data search operations on data storage cartridges without a dependency on host systems, host applications, communications links, etc., as well as a way to efficiently search large amounts of stored data within the data storage cartridges.

SUMMARY

A computer-implemented method according to one embodiment includes initiating a creation of a search index for a data storage cartridge, transparently loading the data storage cartridge into a data storage drive of a data storage library, creating the search index, utilizing the data storage cartridge and the data storage drive, and storing the search index.

In one embodiment, transparently loading the data storage cartridge into the data storage drive of the data storage library includes identifying a host application drive that is not currently being used within the data storage library, loading the data storage cartridge into the host application drive, presenting the host application drive as empty to at least one host application running on at least one host system, and presenting the data storage cartridge as being located in a storage slot.

In this way, a search index may be created for data within a data storage cartridge by one or more of the data storage drive and the library controller. This may eliminate a need to perform the search index creation on one or more host systems/host applications, which may reduce an amount of processing necessary by the host systems/host applications, which may in turn improve a performance of the host systems/host applications.

According to another embodiment, a computer program product for creating a search index within a data storage library includes a computer readable storage medium having program instructions embodied therewith, where the computer readable storage medium is not a transitory signal per se, and where the program instructions are executable by a processor to cause the processor to perform a method including initiating, utilizing the processor, a creation of the search index for a data storage cartridge, transparently loading, utilizing the processor, the data storage cartridge into a data storage drive of a data storage library, creating, utilizing the processor, the search index, utilizing the data storage cartridge and the data storage drive, and storing, utilizing the processor, the search index.

According to another embodiment, a library controller includes a processor, and logic integrated with the processor, executable by the processor, or integrated with and executable by the processor, where the logic is configured to initiate a creation of a search index for a data storage cartridge, transparently load the data storage cartridge into a data storage drive of a data storage library, create the search index, utilizing the data storage cartridge and the data storage drive, and store the search index.

According to another embodiment, a computer-implemented method includes initiating a creation of a search index, transparently loading a first data storage cartridge into a data storage drive within a data storage library, initiating a creation of the search index utilizing the first data storage cartridge and the data storage drive, receiving a request to access data on a second data storage cartridge, utilizing the data storage drive, postponing the creation of the search index utilizing the first data storage cartridge and the data storage drive, removing the first data storage cartridge from the data storage drive, loading the second data storage cartridge into the data storage drive, and providing access to the data on the second data storage cartridge, utilizing the data storage drive.

In one embodiment, removing the first data storage cartridge from the data storage drive further includes transparently loading the first data storage cartridge into a second data storage drive, and resuming the creation of the search index utilizing the first data storage cartridge and the second data storage drive, or restarting the creation of the search index utilizing the first data storage cartridge and the second data storage drive.

In another embodiment, loading the second data storage cartridge includes removing the second data storage cartridge from its home slot, inserting the second data storage cartridge into the data storage drive, updating inventory data to indicate that the second data storage cartridge is not in its home slot, and updating a library map to indicate that the second data storage cartridge is loaded into the data storage drive.

According to another embodiment, a computer-implemented method includes initiating a creation of a search index for a data storage cartridge, transparently loading the data storage cartridge into a data storage drive of a data storage library, including identifying a data storage drive that is not currently being used within the data storage library, and loading the data storage cartridge into the data storage drive, creating the search index, utilizing the data storage cartridge and the data storage drive, and saving the search index.

In this way, by performing the search index creation at the data storage library and drive, instead of a host system and drive, an amount of data sent from the data storage library to the host system may be reduced. For example, instead of sending data from the data storage drive to the host system for search index creation at the host system, the search index may be created at the data storage library. This may result in a decrease in network traffic and bandwidth usage between the data storage drive and host system during a search index creation scenario, and may also improve a performance of components within a communications network between the data storage library and the host system (e.g., one or more switches, etc.).

Any of these embodiments may be implemented in any removable media system. For example, a magnetic data storage system such as a tape drive system, which may include a magnetic head, a drive mechanism for passing a magnetic medium (e.g., recording tape) over the magnetic head, and a controller electrically coupled to the magnetic head.

Other aspects and embodiments of the present invention will become apparent from the following detailed description, which, when taken in conjunction with the drawings, illustrate by way of example the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of an automated data storage library according to one embodiment.

FIG. 2 is a perspective view of a storage frame from the data storage library of FIG. 1.

FIG. 3 is a block diagram of an automated data storage library according to one embodiment.

FIG. 4 is a block diagram depicting a controller configuration according to one embodiment.

FIG. 5A is a front perspective view of a data storage drive according to one embodiment.

FIG. 5B is a rear perspective view of the data storage drive of FIG. 5A.

FIG. 6 is perspective view of a data storage cartridge having a cutaway portion, according to one embodiment.

FIGS. 7A-7B are perspective views of multi-cartridge deep slot cells according to one embodiment.

FIGS. 8A-8D are partial side views of a cartridge blocking mechanism according to one embodiment.

FIG. 9 illustrates a tiered data storage system in accordance with one embodiment.

FIG. 10 illustrates a flowchart of a method for creating a search index within a data storage library, in accordance with one embodiment.

FIG. 11 illustrates a flowchart of a method for transparently managing data storage cartridges, in accordance with one embodiment.

FIG. 12 illustrates an exemplary an exemplary cartridge search index creation environment, in accordance with one embodiment.

DETAILED DESCRIPTION

The following description discloses several preferred embodiments of systems, methods and computer program products for creating a search index within a data storage library. Various embodiments provide a method for transparently loading a data storage cartridge into an available data storage drive, and creating a search index based on data stored within the data storage cartridge.

The following description is made for the purpose of illustrating the general principles of the present invention and is not meant to limit the inventive concepts claimed herein. Further, particular features described herein can be used in combination with other described features in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be given their broadest possible interpretation including meanings implied from the specification as well as meanings understood by those skilled in the art and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless otherwise specified. It will be further understood that the terms “includes” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The following description discloses several preferred embodiments of systems, methods and computer program products for creating a search index within a data storage library.

In one general embodiment, a computer-implemented method includes initiating a creation of a search index for a data storage cartridge, transparently loading the data storage cartridge into a data storage drive of a data storage library, creating the search index, utilizing the data storage cartridge and the data storage drive, and storing the search index.

In another general embodiment, transparently loading the data storage cartridge into the data storage drive of the data storage library includes identifying a host application drive that is not currently being used within the data storage library, loading the data storage cartridge into the host application drive, presenting the host application drive as empty to at least one host application running on at least one host system, and presenting the data storage cartridge as being located in a storage slot.

In this way, a search index may be created for data within a data storage cartridge by one or more of the data storage drive and the library controller. This may eliminate a need to perform the search index creation on one or more host systems/host applications, which may reduce an amount of processing necessary by the host systems/host applications, which may in turn improve a performance of the host systems/host applications.

In another general embodiment, a computer program product for creating a search index within a data storage library includes a computer readable storage medium having program instructions embodied therewith, where the computer readable storage medium is not a transitory signal per se, and where the program instructions are executable by a processor to cause the processor to perform a method including initiating, utilizing the processor, a creation of the search index for a data storage cartridge, transparently loading, utilizing the processor, the data storage cartridge into a data storage drive of a data storage library, creating, utilizing the processor, the search index, utilizing the data storage cartridge and the data storage drive, and storing, utilizing the processor, the search index.

In another general embodiment, a library controller includes a processor, and logic integrated with the processor, executable by the processor, or integrated with and executable by the processor, where the logic is configured to initiate a creation of a search index for a data storage cartridge, transparently load the data storage cartridge into a data storage drive of a data storage library, create the search index, utilizing the data storage cartridge and the data storage drive, and store the search index.

In another general embodiment, a computer-implemented method includes initiating a creation of a search index, transparently loading a first data storage cartridge into a data storage drive within a data storage library, initiating a creation of the search index utilizing the first data storage cartridge and the data storage drive, receiving a request to access data on a second data storage cartridge, utilizing the data storage drive, postponing the creation of the search index utilizing the first data storage cartridge and the data storage drive, removing the first data storage cartridge from the data storage drive, loading the second data storage cartridge into the data storage drive, and providing access to the data on the second data storage cartridge, utilizing the data storage drive.

In another general embodiment, removing the first data storage cartridge from the data storage drive further includes transparently loading the first data storage cartridge into a second data storage drive, and resuming the creation of the search index utilizing the first data storage cartridge and the second data storage drive, or restarting the creation of the search index utilizing the first data storage cartridge and the second data storage drive.

In another general embodiment, loading the second data storage cartridge includes removing the second data storage cartridge from its home slot, inserting the second data storage cartridge into the data storage drive, updating inventory data to indicate that the second data storage cartridge is not in its home slot, and updating a library map to indicate that the second data storage cartridge is loaded into the data storage drive.

In another general embodiment, a computer-implemented method includes initiating a creation of a search index for a data storage cartridge, transparently loading the data storage cartridge into a data storage drive of a data storage library, including identifying a data storage drive that is not currently being used within the data storage library, and loading the data storage cartridge into the data storage drive, creating the search index, utilizing the data storage cartridge and the data storage drive, and saving the search index.

In this way, by performing the search index creation at the data storage library and drive, instead of a host system and drive, an amount of data sent from the data storage library to the host system may be reduced. For example, instead of sending data from the data storage drive to the host system for search index creation at the host system, the search index may be created at the data storage library. This may result in a decrease in network traffic and bandwidth usage between the data storage drive and host system during a search index creation scenario, and may also improve a performance of components within a communications network between the data storage library and the host system (e.g., one or more switches, etc.).

FIGS. 1-2 illustrate an automated data storage library 10 which stores and retrieves data storage cartridges, containing data storage media (not shown), from multi-cartridge deep slot cells 100 and single cartridge storage slots 16. An example of an automated data storage library which has a similar configuration as that depicted in FIGS. 1-2, and may be implemented with some of the various approaches herein is the IBM TS4500 Tape Library. Moreover, it should be noted that references to “data storage media” herein refer to data storage cartridges, and for purposes of the present application, the two terms may be used synonymously.

The library 10 of FIG. 1 comprises a left hand service bay 13, one or more storage frames 11, and right hand service bay 14. As will be discussed in further detail below, a frame may comprise an expansion component of the library. Thus, storage frames may be added or removed to expand or reduce the size and/or functionality of the library. According to different approaches, frames may include additional storage slots, deep slot cells, drives, import/export stations, accessors, operator panels, etc.

FIG. 2 shows an exemplary embodiment of a storage frame 11, which acts as the base frame of the library 10. Moreover, the storage frame 11 illustrated in FIG. 2 is contemplated to be a minimum configuration of the library 10, for which there is only a single accessor 18 (i.e., there are no redundant accessors) and no service bay. However, in other embodiments, a storage frame may include multiple robotic accessors and/or service bays.

Looking to FIG. 2, the library 10 is arranged for accessing data storage media in response to commands from at least one external host system (not shown). The library 10 includes a plurality of storage slots 16 on front wall 17 and a plurality of multi-cartridge deep slot cells 100 on rear wall 19, both of which may be used for storing data storage cartridges that may comprise data storage media. According to one approach, the storage slots 16 are configured to store a single data storage cartridge, and the multi-cartridge deep slot cells 100 are configured to store a plurality of data storage cartridges. In a preferred approach, the multi-cartridge deep slot cells may be arranged in sequential order of tiers from front to rear (e.g., see FIG. 7A).

With continued reference to FIG. 2, the storage frame 11 of the library 10 also includes at least one data storage drive 15, e.g., for reading and/or writing data with respect to the data storage media. Additionally, a first accessor 18 may be used to transport data storage media between the plurality of storage slots 16, the multi-cartridge deep slot cells, and/or the data storage drive(s) 15. According to various approaches, the data storage drives 15 may be optical disc drives, magnetic tape drives, solid state drives having nonvolatile random access memory (NVRAM) such as Flash memory, or other types of data storage drives as are used to read and/or write data with respect to the data storage media.

As illustrated, the storage frame 11 may optionally include an operator panel or other user interface, such as a web-based interface, which allows a user to interact with the library 10. The storage frame 11 may also optionally comprise an upper I/O station 24 and/or a lower I/O station 25, thereby allowing data storage cartridges to be added (e.g., inserted) to the library inventory and/or removed from the library without disrupting library operation. Furthermore, the library 10 may have one or more storage frames 11, each having storage slots 16, preferably accessible by the first accessor 18.

As described above, the storage frames 11 may be configured with different components depending upon the intended function. One configuration of storage frame 11 may comprise storage slots 16 and/or multi-cartridge deep slot cells 100, data storage drive(s) 15, and other optional components to store and retrieve data from the data storage cartridges. However, in another approach, a storage frame 11 may include storage slots 16 and/or multi-cartridge deep slot cells 100 and no other components. The first accessor 18 may have a gripper assembly 20, e.g., for gripping one or more data storage media, in addition to having a bar code scanner or other reading system, such as a cartridge memory reader or similar system mounted on the gripper assembly 20, to “read” identifying information about the data storage media.

FIG. 3 depicts an automated data storage library 10, in accordance with one embodiment. As an option, the present automated data storage library 10 may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS. Of course, however, such automated data storage library 10 and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the automated data storage library 10 presented herein may be used in any desired environment. Thus FIG. 3 (and the other FIGS.) should be deemed to include any and all possible permutations.

Referring now to FIG. 3, the automated data storage library 10 as described in reference to FIGS. 1 and 2, is depicted according to one embodiment. According to a preferred approach, the library 10 may employ a controller, e.g., arranged as a distributed system of modules with a plurality of processor nodes.

In one approach, the library is controlled, not by a central controller, but rather, by a distributed control system for receiving logical commands and converting the commands to physical movements of the accessor and gripper, and for operating the automated data storage library 10 in accordance with the desired physical movements. The distributed control system may also provide logistical support, such as responding to host requests for element status, inventory, library status, etc. The specific commands, the conversion of those commands to physical movements, and the operation of the drives may be of a type known to those of skill in the art.

While the automated data storage library 10 has been described as employing a distributed control system, various other approaches described and/or suggested herein may be implemented in automated data storage libraries regardless of control configuration, such as, but not limited to, an automated data storage library having one or more library controllers that are not distributed.

Referring still to FIG. 3, the library 10 may have one or more storage frames 11, a left hand service bay 13 and a right hand service bay 14. The left hand service bay 13 is shown with a first accessor 18, where, as discussed above, the first accessor 18 may include a gripper assembly 20 and/or a bar code scanner (e.g., reading system) to “read” identifying information about the data storage media depending on the desired embodiment. Furthermore, the right hand service bay 14 is shown having a second accessor 28, which includes a gripper assembly 30 and may also include a reading system 32 to “read” identifying information about the data storage media.

According to one approach, in the event of a failure or other unavailability of the first accessor 18, or its gripper assembly 20, etc., the second accessor 28 may perform some or all of the functions of the first accessor 18. Thus in different approaches, the two accessors 18, 28 may share one or more mechanical paths, they may have completely independent mechanical paths, or combinations thereof. In one example, the accessors 18, 28 may have a common horizontal rail with independent vertical rails to travel therealong. Moreover, it should be noted that the first and second accessors 18, 28 are described as first and second for descriptive purposes only and this description is not meant to limit either accessor to an association with either the left hand service bay 13, or the right hand service bay 14.

In an exemplary embodiment which is in no way intended to limit the invention, the first and second accessors 18, 28 may preferably move their grippers in at least two directions, called the horizontal “X” direction and vertical “Y” direction, e.g., to retrieve and grip, deliver and release, load and unload, etc. the data storage cartridge at the storage slots 16, multi-cartridge deep slot cells 100, data storage drives 15, etc.

With continued reference to FIG. 3, library 10 receives commands from one or more host systems 40, 41, 42. The host systems 40, 41, 42, such as host servers, communicate with the library directly, e.g., on path 80, through one or more control ports (not shown), or through one or more data storage drives 15 on paths 81, 82. Thus, in different approaches, the host systems 40, 41, 42 may provide commands to access particular data storage cartridges and move the cartridges, for example, between the storage slots 16 and the data storage drives 15. The commands are typically logical commands identifying the cartridges or cartridge media, and/or logical locations for accessing the media. Furthermore, it should be noted that the terms “commands” and “work requests” are used interchangeably herein to refer to such communications from the host system 40, 41, 42 to the library 10 as are intended to result in accessing particular data storage media within the library 10 depending on the desired approach.

According to one embodiment, the library 10 may be controlled by a library controller. Moreover, in various approaches, the library controller may include a distributed control system receiving the logical commands from hosts, determining the required actions, and/or converting the actions to physical movements of the first and/or second accessor 18, 28. In another approach, the distributed control system may have a plurality of processor nodes, each having one or more computer processors. According to one example of a distributed control system, a communication processor node 50 may be located in a storage frame 11. The communication processor node provides a communication link for receiving the host commands, either directly or through the drives 15, via at least one external interface, e.g., coupled to line 80.

Still referring to FIG. 3, the communication processor node 50 may additionally provide a communication link 70 for communicating with the data storage drives 15. As illustrated, the communication processor node 50 may preferably be located in the storage frame 11, e.g., close to the data storage drives 15. Furthermore, one or more additional work processor nodes may be provided to form an exemplary distributed processor system, which may comprise, e.g., a work processor node 52 located at first accessor 18, and that is coupled to the communication processor node 50 via a network 60, 157. According to different approaches, each work processor node may respond to received commands that are broadcast thereto from any communication processor node, and the work processor nodes may also direct the operation of the accessors, e.g., providing move commands. An XY processor node 55 may be provided and may be located at an XY system of first accessor 18. As illustrated, the XY processor node 55 is coupled to the network 60, 157, and is responsive to the move commands, operating the XY system to position the gripper assembly 20.

Also, an operator panel processor node 59 may be provided at the optional operator panel for providing an interface for communicating between the operator panel and the communication processor node 50, the work processor nodes 52, 252, and the XY processor nodes 55, 255.

A network 60, for example comprising a common bus, is provided, coupling the various processor nodes. The network may comprise a robust wiring network, such as the commercially available Controller Area Network (CAN) bus system, which is a multi-drop network, having a standard access protocol and wiring standards, for example, as defined by CiA, the CAN in Automation Association, Am Weich Selgarten 26, D-91058 Erlangen, Germany. Other networks, such as Ethernet, or a wireless network system, such as RF or infrared, may be employed in the library as is known to those of skill in the art. In addition, multiple independent networks may also be used to couple the various processor nodes.

As illustrated in FIG. 3, the communication processor node 50 is coupled to each of the data storage drives 15 of a storage frame 11, via lines 70, and are thereby communicating with the drives 15 and with host systems 40, 41, 42. Alternatively, the host systems 40, 41, 42 may be directly coupled to the communication processor node 50, at input 80 for example, or to control port devices (not shown) which connect the library to the host system(s) with a library interface similar to the drive/library interface. As is known to those of skill in the art, various communication arrangements may be employed for communication with the hosts and with the data storage drives. In the example of FIG. 3, host connections 80 and 81 are intended to be Ethernet and a SCSI bus, respectively, e.g., and may serve as host connections. However, bus 82 comprises an example of a Fibre Channel bus which is a high speed serial data interface, allowing transmission over greater distances than the SCSI bus systems.

According to some approaches, the data storage drives 15 may be in close proximity to the communication processor node 50, and may employ a short distance communication scheme, such as Ethernet, or a serial connection, such as RS-422. Thus the data storage drives 15 may be individually coupled to the communication processor node 50 by lines 70. Alternatively, the data storage drives 15 may be coupled to the communication processor node 50 through one or more networks.

Furthermore, additional storage frames 11 may be provided, whereby each is preferably coupled to the adjacent storage frame. According to various approaches, any of the additional storage frames 11 may include communication processor nodes 50, storage slots 16, data storage drives 15, networks 60, etc.

Moreover, as described above, the automated data storage library 10 may comprise a plurality of accessors. A second accessor 28, for example, is shown in a right hand service bay 14 of FIG. 3. The second accessor 28 may include a gripper assembly 30 for accessing the data storage media, and an XY system 255 for moving the second accessor 28. The second accessor 28 may run on the same horizontal mechanical path as the first accessor 18, and/or on an adjacent (e.g., separate) path. Moreover the illustrative control system additionally includes an extension network 200 which forms a network coupled to network 60 of the storage frame(s) 11 and to network 157 of left hand service bay 13.

In FIG. 3 and the accompanying description, the first and second accessors are associated with the left hand service bay 13 and the right hand service bay 14 respectively. However, this is for illustrative purposes and there may not be an actual association. Thus, according to another approach, network 157 may not be associated with the left hand service bay 13 and network 200 may not be associated with the right hand service bay 14. Moreover, depending on the design of the library, it may not be necessary to have a left hand service bay 13 and/or a right hand service bay 14 at all.

An automated data storage library 10 typically comprises one or more controllers to direct the operation of the automated data storage library. Moreover, host computers and data storage drives typically include similar controllers. A library controller may take many different forms and may comprise, for example, but is not limited to, an embedded system, a distributed control system, a personal computer, a workstation, etc. The term “library controller” as used herein is intended in its broadest sense as a device that includes at least one processor, and optionally further circuitry and/or logic, for controlling and/or providing at least some aspects of library operations.

Referring now to FIG. 4, a typical controller 400 is shown with a processor 402, Random Access Memory (RAM) 403, nonvolatile memory 404, device specific circuits 401, and I/O interface 405. Alternatively, the RAM 403 and/or nonvolatile memory 404 may be contained in the processor 402 as could the device specific circuits 401 and I/O interface 405. The processor 402 may comprise, for example, an off-the-shelf microprocessor, custom processor, Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), discrete logic, etc. The RAM 403 is typically used to hold variable data, stack data, executable instructions, etc.

According to various approaches, the nonvolatile memory 404 may comprise any type of nonvolatile memory such as, but not limited to, Electrically Erasable Programmable Read Only Memory (EEPROM), flash Programmable Read Only Memory (PROM), battery backup RAM, hard disk drives, etc. However, the nonvolatile memory 404 is typically used to hold the executable firmware and any nonvolatile data. Moreover, the I/O interface 405 comprises a communication interface that allows the processor 402 to communicate with devices external to the controller. Examples may comprise, but are not limited to, serial interfaces such as RS-232, USB (Universal Serial Bus) or Small Computer Systems Interface (SCSI). The device specific circuits 401 provide additional hardware to enable the controller 400 to perform unique functions including, but not limited to, motor control of a cartridge gripper. Moreover, the device specific circuits 401 may include electronics that provide, by way of example but not limitation, Pulse Width Modulation (PWM) control, Analog to Digital Conversion (ADC), Digital to Analog Conversion (DAC), etc. In addition, all or part of the device specific circuits 401 may reside outside the controller 400.

While the automated data storage library 10 is described as employing a distributed control system, the various approaches described and/or suggested herein may be implemented in various automated data storage libraries regardless of control configuration, including, but not limited to, an automated data storage library having one or more library controllers that are not distributed. Moreover, a library controller may comprise one or more dedicated controllers of a library, depending on the desired embodiment. For example, there may be a primary controller and a backup controller. In addition, a library controller may comprise one or more processor nodes of a distributed control system. According to one example, communication processor node 50 (e.g., of FIG. 3) may comprise the library controller while the other processor nodes (if present) may assist the library controller and/or may provide backup or redundant functionality. In another example, communication processor node 50 and work processor node 52 may work cooperatively to form the library controller while the other processor nodes (if present) may assist the library controller and/or may provide backup or redundant functionality. Still further, all of the processor nodes may comprise the library controller. According to various approaches described and/or suggested herein, a library controller may have a single processor or controller, or it may include multiple processors or controllers.

FIGS. 5A-5B illustrate the front 501 and rear 502 views of a data storage drive 15, according to one embodiment. In the example depicted in FIGS. 5A-5B, the data storage drive 15 comprises a hot-swap drive canister, which is in no way intended to limit the invention. In fact, any configuration of data storage drive may be used whether or not it includes a hot-swap canister. As discussed above, a data storage drive 15 is used to read and/or write data with respect to the data storage media, and may additionally communicate with a memory which is separate from the media, and is located within the cartridge. Thus, according to one approach, a data storage cartridge may be placed into the data storage drive 15 at opening 503.

Furthermore, FIG. 6 illustrates an embodiment of a data storage cartridge 600 with a cartridge memory 610 shown in a cutaway portion of the Figure, which is in no way intended to limit the invention. In fact, any configuration of data storage cartridge may be used whether or not it comprises a cartridge memory. According to various approaches, media of the data storage cartridge media may include any type of media on which data may be stored, including but not limited to magnetic media, e.g., magnetic tape, disks, etc.; optical media, e.g., optical tape, discs, etc.; electronic media, e.g., PROM, EEPROM, flash PROM, CompactFlash™, Smartmedia™, Memory Stick™, etc.; etc., or other suitable media. Moreover, an example of a data storage cartridge that is widely employed in automated data storage libraries for mass data storage is a magnetic tape cartridge in which the media is magnetic tape.

Looking now to FIGS. 7A-7B, a multi-cartridge deep slot cell 100 having biasing springs 152 is depicted according to one embodiment. As shown in the illustrative embodiment, the multi-cartridge deep slot cell 100 comprises a housing 110 defining an interior space 115. Furthermore, a plurality of storage slots 120 is disposed within the housing, and may be configured for storing up to a plurality of data storage cartridges 600, depending on the desired approach. Alternatively, the multi-cartridge deep slot cell 100 may be built into the frame of the automated data storage library according to one approach.

FIGS. 8A-8D illustrate an embodiment of a cartridge blocking mechanism 150 having a retaining gate 660 that retains the data storage cartridges in the multi-cartridge deep slot cell 100 according to one embodiment. As illustrated, according to one approach, the retaining gate 660 may be externally attached to a multi-cartridge deep slot cell 100, relative to a front opening of the multi-cartridge deep slot cell 100, whereby the retaining gate 660 can be activated by an accessor 18, e.g., of an automated tape library. Moreover, the retaining gate 660 allows for positive cartridge retention against the pressure of biasing springs (see 152 of FIGS. 7A-7B), and ensures that one or more data storage cartridges do not get pushed out of the multi-cartridge deep slot cell 100 simultaneously, while allowing the pushing mechanism (not shown) of the multi-cartridge deep slot cell 100 to continuously push data storage cartridge(s) to the opening in a multi-cartridge deep slot cell 100. Thus, according to one approach, the accessor 18 may open the retaining gate to gain access to the data storage cartridge in tier 1 and, upon its extraction, the biasing spring 152 moves the cartridge(s) positioned behind the extracted cartridge forward, thereby promoting the cartridge(s) by one tier as will soon become apparent.

The basic working of the retaining gate is that the gate prevents the data storage cartridge(s) from being pushed out of a multi-cartridge deep slot cell 100. For example, as shown in FIGS. 8A-8D, a retaining gate 660 can be lifted by, for example, accessor 18 or by a front storage cartridge 642 for cartridge removal from/insertion into a multi-cartridge deep slot cell 100. Specifically, retaining gate 660 has a pivoting arm 661 mounted on multi-cartridge deep slot cell 100 via a pivoting post (not shown) that can be integral to a construction of multi-cartridge deep slot cell 100. Pivoting arm 661 is located below a catch 662 of retaining gate 660 whereby a thrust force TF through data storage cartridge 644-642 caused by the pushing mechanism (not shown) of multi-cartridge deep slot cell 100 causes retaining gate 660 to stay closed in a retaining position as shown in FIG. 8A. Moreover, the retaining gate 660 is preferably biased such that it closes in the downward direction over the front opening of multi-cartridge deep slot cell 100. This constant biasing may be achieved via gravity as shown in FIG. 8A or by implementing a spring force, e.g., attached to retaining gate 660 (not shown).

For removal of front storage cartridge 642 by accessor 18 from multi-cartridge deep slot cell 100, retaining gate 660 must be lifted upward to a releasing position whereby catch 662 of retaining gate 660 is disengaged from front storage cartridge 642. This can be seen in FIG. 8B where accessor 18 interfaces with retaining gate 660 by providing a lifting force. Once retaining gate 660 is lifted to the releasing position and accessor 18 is engaged with storage cartridge 642, accessor 18 can pull storage cartridge 642 out of multi-cartridge deep slot cell 100 and into accessor 18 without any interference of retaining gate 660 as shown in FIG. 8C. In view of storage cartridges 644 and 643 being stored in multi-cartridge deep slot cell 100, retaining gate 660 must return to its retaining position to prevent storage cartridges 644 and 643 from being ejected from multi-cartridge deep slot cell 100 by the thrust force TF of the pushing mechanism (not shown). During extraction of front storage cartridge 642 through the front opening of multi-cartridge deep slot cell 100, the retaining gate 660, which is being biased downward, moves back to the retaining position to engage storage cartridge 643.

Once front storage cartridge 642 is extracted and storage cartridges 643 and 644 are retained from being pushed out of multi-cartridge deep slot cell 100, retaining gate 660 has successfully completed its cartridge retrieval process. Now retaining gate 660 demonstrates its ability to work for cartridge insertion into multi-cartridge deep slot cell 100. When accessor 18 begins to insert storage cartridge 642 back into multi-cartridge deep slot cell 100, retaining gate 660 is lifted to its releasing position to allow storage cartridge 642 through the front opening of multi-cartridge deep slot cell 100. Catch 662 of retaining gate 660 interfaces with a rear portion of storage cartridge 642, in particular a beveled surface of catch 662 as shown in FIG. 8D, whereby retaining gate 660 is lifted to its releasing position as shown in FIG. 8B due to storage cartridge 642 being pushed in multi-cartridge deep slot cell 100 by accessor 18. In doing so, storage cartridges 644, 643 are pushed deeper into multi-cartridge deep slot cell 100 by storage cartridge 642 in multi-cartridge deep slot cell 100 by accessor 18. Thus, the accessor is able to provide a force greater than the thrust force TF antiparallel thereto, to overcome the directional biasing of the storage cartridges 644, 643. Upon full insertion into multi-cartridge deep slot cell 100, retaining gate 660 moves to its retaining position to engage storage cartridge 642 as shown in FIG. 8A.

Thus, looking to various embodiments presented herein, access to a storage slot may include the ability to remove a cartridge from a storage slot, the ability to place a cartridge into a storage slot, or combinations thereof.

According to an exemplary embodiment, the storage slots from top to bottom are considered to be in parallel and comprise the same tier. Moreover, the storage slots from front to back, in a particular row, are considered to be in series and comprise sequential tiers.

Referring back to FIGS. 7A-7B, in accordance with one embodiment, storage slots 120 are depicted as being configured for storing up to a plurality of data storage cartridges 600, and arranged in sequential order of tiers 621, 622, 623, 624, 625 from front to rear. It should be noted that the frontmost tier 621 is also called “tier 1”, while the next tier 622 is called “tier 2”, etc., and the last tier 625 is also called the “rearmost” tier. However, referring to FIG. 2, in one embodiment, the single cartridge storage slots 16 are also termed “tier 0”.

Referring again to FIGS. 1-3, according to one embodiment, the controller of automated data storage library 10 may operate the accessor(s) 18, 28 to selectively extract, place and/or transport data storage cartridges with respect to the multi-cartridge deep slot cells 100 and/or other elements of the automated data storage library 10. For example, the controller may facilitate extracting a cartridge from a multi-cartridge deep slot cell 100, transporting the cartridge to a data storage drive 15 and placing the cartridge in the drive 15. The controller may then extract the cartridge from the data storage drive 15, while directing the accessor to transport the cartridge to a specific multi-cartridge deep slot cell 100, and place the cartridge therein.

In one embodiment, one or more data storage cartridges may be added into the library, e.g., at an I/O station 24, 25, whereby the controller of the automated data storage library 10 may then operate the accessor(s) 18, 28 to transport the cartridge(s) to specific multi-cartridge deep slot cell(s) 100, and place the cartridge(s) therein. Similarly, the controller may operate the accessor(s) to selectively extract, place and transport data storage cartridges with respect to the single cartridge storage slots 16, and/or transport inserted or added cartridge(s) to specific single cartridge storage slots 16.

Now referring to FIG. 9, a storage system 900 is shown according to one embodiment. Note that some of the elements shown in FIG. 9 may be implemented as hardware and/or software, according to various embodiments. In some approaches, the storage system 900 may be implemented in an automated data storage library such as that shown in FIGS. 1-2. In other approaches, an automated data storage library such as that shown in FIGS. 1-2 may be a tier of the storage system 900.

The storage system 900 may include a storage system manager 912 for communicating with a plurality of media on at least one higher storage tier 902 and at least one lower storage tier 906. The higher storage tier(s) 902 preferably may include one or more random access and/or direct access storage media 904, such as hard disks in hard disk drives (HDDs), nonvolatile memory (NVM), solid state memory in solid state drives (SSDs), flash memory, SSD arrays, flash memory arrays, etc., and/or others noted herein or known in the art. The lower storage tier(s) 906 may preferably include one or more lower performing storage media 908, including sequential access media such as magnetic tape in tape drives and/or optical media, slower accessing HDDs, slower accessing SSDs, etc., and/or others noted herein or known in the art. One or more additional storage tiers 916 may include any combination of storage memory media as desired by a designer of the system 900. Also, any of the higher storage tiers 902 and/or the lower storage tiers 906 may include some combination of storage devices and/or storage media.

The storage system manager 912 may communicate with the storage media 904, 908 on the higher storage tier(s) 902 and lower storage tier(s) 906 through a network 910, such as a storage area network (SAN), as shown in FIG. 9, or some other suitable network type. The storage system manager 912 may also communicate with one or more host systems (not shown) through a host interface 914, which may or may not be a part of the storage system manager 912. The storage system manager 912 and/or any other component of the storage system 900 may be implemented in hardware and/or software, and may make use of a processor (not shown) for executing commands of a type known in the art, such as a central processing unit (CPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc. Of course, any arrangement of a storage system may be used, as will be apparent to those of skill in the art upon reading the present description.

In more embodiments, the storage system 900 may include any number of data storage tiers, and may include the same or different storage memory media within each storage tier. For example, each data storage tier may include the same type of storage memory media, such as HDDs, SSDs, sequential access media (tape in tape drives, optical disc in optical disc drives, etc.), direct access media (CD-ROM, DVD-ROM, etc.), or any combination of media storage types. In one such configuration, a higher storage tier 902, may include a majority of SSD storage media for storing data in a higher performing storage environment, and remaining storage tiers, including lower storage tier 906 and additional storage tiers 916 may include any combination of SSDs, HDDs, tape drives, etc., for storing data in a lower performing storage environment. In this way, more frequently accessed data, data having a higher priority, data needing to be accessed more quickly, etc., may be stored to the higher storage tier 902, while data not having one of these attributes may be stored to the additional storage tiers 916, including lower storage tier 906. Of course, one of skill in the art, upon reading the present descriptions, may devise many other combinations of storage media types to implement into different storage schemes, according to the embodiments presented herein.

According to some embodiments, the storage system (such as 900) may include logic configured to receive a request to open a data set, logic configured to determine if the requested data set is stored to a lower storage tier 906 of a tiered data storage system 900 in multiple associated portions, logic configured to move each associated portion of the requested data set to a higher storage tier 902 of the tiered data storage system 900, and logic configured to assemble the requested data set on the higher storage tier 902 of the tiered data storage system 900 from the associated portions. Of course, this logic may be implemented as a method on any device and/or system or as a computer program product, according to various embodiments.

Now referring to FIG. 10, a flowchart of a method 1000 is shown according to one embodiment. The method 1000 may be performed in accordance with the present invention in any of the environments depicted in FIGS. 1-9 and 12, among others, in various embodiments. Of course, more or less operations than those specifically described in FIG. 10 may be included in method 1000, as would be understood by one of skill in the art upon reading the present descriptions.

Each of the steps of the method 1000 may be performed by any suitable component of the operating environment. For example, in various embodiments, the method 1000 may be partially or entirely performed by one or more servers, computers, or some other device having one or more processors therein. The processor, e.g., processing circuit(s), chip(s), and/or module(s) implemented in hardware and/or software, and preferably having at least one hardware component may be utilized in any device to perform one or more steps of the method 1000. Illustrative processors include, but are not limited to, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., combinations thereof, or any other suitable computing device known in the art.

As shown in FIG. 10, method 1000 may initiate with operation 1002, where a creation or update of a search index for one or more data storage cartridges is initiated. Herein, creation of a search index may refer to the creation of a search index or an update to an existing search index with respect to one or more data storage cartridges. In one embodiment, the creation of the search index may be initiated within a data storage library. In another embodiment, the creation of the search index may be initiated via a management interface of a data storage library.

For example, after firmware that supports search capability is installed within the data storage library, a search index generation operation may be received via a web user interface of the data storage library. In another example, after pre-written data storage cartridges have been bulk loaded into the data storage library, a search index generation operation may be received via a web user interface of the data storage library.

Additionally, in one embodiment, the creation of the search index may be initiated in response to the receipt of a search request (e.g., via the management interface, etc.). For example, the creation of the search index may be initiated in response to receiving a search request for data in the data storage library. In another example, the search request may be initially received utilizing one or more management interfaces of the data storage library. For instance, the search request may be received from an entity (e.g., one or more of a user, an application, etc.), using one or more management interfaces. In another example, the one or more management interfaces may include one or more of a remote network interface, a web user interface, a graphical user interface (GUI), an operator panel operatively coupled to the data storage library, a command line interface supported by the data storage library, an application programming interface (API), a simple network management protocol (SNMP) interface, etc. In another embodiment, the one or more management interfaces may send the search request to a library controller of the data storage library.

Further, in one embodiment, the creation of the search index may be initiated as part of a search operation. In another embodiment, the creation of the search index may be initiated in response to the receipt of a request to create the search index for the data storage cartridge. In another embodiment, the request may be received from a host system. For example, a search request, search index creation request, etc. may be received from a host application running within the host system. In another embodiment, the host application may include an application running within the host system that accesses the data storage library (e.g., to read and write data to and from data storage cartridges within the library, etc.). In yet another embodiment, the host application may include a backup application running on the host system.

In another embodiment, the creation of the search index may be initiated automatically according to one or more predetermined criteria. For example, a search index may be periodically created/updated for one or more data storage cartridges within the data storage library according to the predetermined schedule. In another example, the data storage library may perform the index operation according to a predetermined date and/or time. In yet another example, the data storage library may perform the index operation in response to new data being introduced into the data storage library. Still further, the data storage library may initiate a creation or update of the search index when the data storage library is or becomes idle (e.g., when the data storage library is not performing any host media access operations) and/or when one or more data storage drives are or become idle.

In another example, creation of the search index may be initiated in response to existing data being removed from the data storage library. In yet another example, creation of the search index may be initiated in response to an identified writing and/or erasing of data from within the data storage library.

Further still, in one embodiment, the search index may include an addition to/modification of an existing search index. In another embodiment, the data storage cartridge may be one of a plurality of data storage cartridges for which a search index is to be created.

Also, method 1000 may proceed with operation 1004, where the one or more data storage cartridges are transparently loaded into one or more data storage drives of a data storage library. Transparent loading may refer to concealing (from one or more host applications) the fact that a drive is loaded with a data storage cartridge for use in creating/updating a search index. For example, the library may report the drive as being empty and/or it may instruct the data storage drive to report itself as being empty, when a cartridge is loaded in the data storage drive. Alternatively, transparently may refer to the use of a utility or spare drive that is not within the scope or view of one or more host applications so there is no need to falsely report the drive as being as being empty. In addition, transparent loading may refer to concealing (from one or more host applications) the location of a data storage cartridge. For example, the library may report a cartridge as being in its home slot when it is really loaded in a data storage drive. In one embodiment, a data storage cartridge may be selected based on information found within the search request. For example, the search request may include an identification of one or more cartridges to be searched. In another embodiment, the data storage cartridge may be selected based on one or more characteristics of an entity from which the search request is received.

For example, one or more characteristics of the entity may include a level of access and/or one or more permissions associated with the entity. In another example, the request may include an access/permissions level associated with the entity that initiated the request. In yet another example, the one or more characteristics may include an identifier of the entity that initiated the request. For instance, the identifier may be included within the request. In another example, the identifier may be referenced in order to determine an access level associated with the entity, one or more cartridges associated with the entity, etc. In another embodiment, the data storage cartridge may be selected in response to a determination that data within the data storage cartridge is accessible by the entity, is owned by the entity, is associated with the entity, etc.

Also, in one embodiment, a plurality of cartridges may be transparently loaded into a plurality of data storage drives within the data storage library. In another embodiment, loading the data storage cartridge may include sending one or more instructions to a robotic mechanism (e.g., an accessor, etc.) to physically select the data storage cartridge and move it into the data storage drive.

In addition, in one embodiment, the data storage drive may include a host application drive. For example, the host application drive may include a data storage drive of the data storage library that is accessible/viewable by one or more host applications. In another example, the data storage cartridge may be transparently loaded into a host application drive of the data storage library.

For instance, the library controller may identify a host application drive that is not currently being used within the data storage library. In one embodiment, the library controller may then automatically load the data storage cartridge into the host application drive. In another embodiment, the host application drive may be presented as empty to all host applications running on host systems. For example, if a host application requests a library map (e.g., element address table, inventory data, etc.) from the library controller, the library controller may provide a library map to the host application indicating that the data storage drive is empty.

Furthermore, in one embodiment, the data storage drive may include a utility drive. For example, the utility drive may include a data storage drive of the data storage library that is not accessible/viewable by any host applications. In another embodiment, the library controller may identify a utility drive that is not currently being used within the data storage library, and may transparently load the data storage cartridge into the utility drive of the data storage library. In yet another embodiment, the data storage cartridge may be presented by the library controller as being in its home slot.

For example, if a host application requests inventory data from the library controller, the library controller may provide inventory data to the host application indicating that the data storage cartridge is in its home slot, and not in the utility drive. In this way, the utility drive may not be visible by host applications, and may therefore not have to be instructed to identify as empty if its status is queried by any host application. In yet another embodiment, a plurality of cartridges may be transparently loaded into both one or more host application drives and one or more utility drives simultaneously, in response to receiving the search index request.

Further still, in one embodiment, the data storage drive may be instructed to identify as empty if its status is queried by any host application. In this way, the data storage drive may appear as empty/open/accessible by both the library controller and the data storage drive itself. In another embodiment, the transparently loaded data storage cartridge may be presented by the library controller as being in its home slot. For example, the library controller may receive a request from a host application for inventory data, and in response, the library controller may provide inventory data to the host application indicating that the data storage cartridge is in its home slot, and not in the data storage drive.

Also, method 1000 may proceed with operation 1006, where the search index is created or updated, utilizing the one or more data storage cartridges and the one or more data storage drives. The data storage library may create/update the search index based on read commands sent to the one or more data storage drives or the one or more data storage drives may assist with the indexing of data on the data storage cartridge, as will be discussed. In one embodiment, the search index may include a search engine index. For example, the search index may include collected, parsed, and stored data used by one or more search engines to perform a search for data within the data storage cartridge.

Additionally, in one embodiment, the data may be collected from a data storage cartridge, and may be subsequently parsed and stored in one or more data structures. In another embodiment, the stored data may be referenced during a search for data stored within the data storage cartridge in order to reduce a time spent searching the data, maximize an effectiveness of the search, etc.

Further, in one embodiment, the search index may be created by a data storage drive for data stored in the data storage cartridge. In another embodiment, creating the search index may include parsing the data stored within the data storage cartridge by the data storage drive. For example, textual data stored within the data storage cartridge may include words that are broken apart for insertion as tokens into the search index.

In another example, the document parsing may include one or more of tokenization, word boundary disambiguation, tagging, text segmentation, content analysis, text analysis, text mining, concordance generation, speech segmentation, lexing, lexical analysis, etc. In yet another example, the search index may be created utilizing the parsed data.

Further still, in one embodiment, creating the search index may include creating one or more index data structures by the data storage drive, based on the data within the data storage cartridge. For example, the one or more index data structures may include one or more of a suffix tree, an inverted index, a citation index, an n-gram index, a document-term matrix, etc.

Also, in one embodiment, the search index may be created utilizing hardware/firmware/software of the data storage drive. For example, the data storage drive may include indexing functionality that parses the data storage within the data storage cartridge and creates the search index, based on the parsing. In another embodiment, the search index may be created by the data storage drive in response to one or more commands sent to the data storage drive.

For example, the one or more commands may include one or more read and/or write commands. In another example, the one or more commands may be sent to the data storage drive by a library controller. In yet another example, the one or more commands/instructions may be sent to the data storage drive by a host system via a management interface of the data storage library. In still another example, a library controller may instruct the data storage drive to perform the search index creation. For instance, the library controller may provide one or more parameters (e.g., parameters to be used during the creation of the search index, etc.) to the data storage drive.

In addition, in one embodiment, the created search index may be compressed. For example, data comprising the created search index may be compressed in order to reduce a size of the search index. In another example, the search index may be compressed at the data storage drive. In yet another example, the search index may be compressed by the data storage drive utilizing functionality provided by the data storage drive. In still another example, the search index may be compressed by the data storage drive in response to one or more commands sent to the data storage drive.

Furthermore, in one embodiment, one or more parameters of the search index may be adjusted. For example, the parameters may include a size of the search index, a type of compression used to compress the search index, etc. These parameters may include parameters sent to the data storage drive by a library controller, a host system, etc. In another embodiment, a search index may be created for data stored at a plurality of different data storage cartridges within the data storage library.

Further still, method 1000 may proceed with operation 1008, where the search index is stored. In one embodiment, all or part of the created search index may be stored within the data storage cartridge (e.g., the data storage cartridge storing the data for which the search index was created). In another embodiment, all or part of the created search index may be stored within another data storage cartridge (e.g., separate from the data storage cartridge storing the data for which the search index was created). For example, the other data storage cartridge may include a data storage cartridge dedicated to storing one or more search indices for data stored at a plurality of different data storage cartridges within the data storage library.

Additionally, in one embodiment, all or part of the created search index may be stored within media other than the data storage cartridge. For example, all or part of the created search index may be stored within one or more hard drives, flash drives, solid state drives (SSDSs), tape drives, optical drives, cloud storage, etc. In another example, all or a portion of the media other than the data storage cartridge may be located within the data storage library. In yet another example, all or a portion of the media other than the data storage cartridge may be located outside the data storage library. In still another example, the media other than the data storage cartridge may be removably coupled to the data storage drive.

Further, in one embodiment, if the search index is stored on one or more data storage cartridges within the data storage library, the search index may be accessed by transparently loading the one or more data storage cartridges into one or more data storage drives of the data storage library.

In another embodiment, a search may be performed, utilizing the search index. For example, a search query may be received at the data storage library (e.g., utilizing a management interface of the data storage library, etc.). The search query may include a request to search data stored within the data storage cartridge. In response to receiving the search query, the search index may be retrieved (e.g., from within one or more storage cartridges within the data storage library, from a cloud computing environment, from removable media, from a hard drive, etc.). The search may then be performed, utilizing the search index. For example, the search query may be compared against the search index in order to determined one or more search results. The search results may then be returned.

In one embodiment, the search results may be returned to an entity from which the search request was obtained. In another embodiment, the search results may be returned utilizing a management interface by which the search request was received. In yet another embodiment, the search results may be returned utilizing a different management interface from which the search request was received.

In this way, a search index may be created for data within a data storage cartridge by one or more of the data storage drive and the library controller. This may eliminate a need to perform the search index creation on one or more host systems/host applications, which may reduce an amount of processing necessary by the host systems/host applications, which may in turn improve a performance of the host systems/host applications.

Additionally, by performing the search index creation at the data storage library and drive, instead of a host system and drive, an amount of data sent from the data storage library to the host system may be reduced. For example, instead of sending data from the data storage drive to the host system for search index creation at the host system, the search index may be created at the data storage library. This may result in a decrease in network traffic and bandwidth usage between the data storage drive and host system during a search index creation scenario, and may also improve a performance of components within a communications network between the data storage library and the host system (e.g., one or more switches, etc.).

Further, by performing the search index creation at the data storage library instead of a host system the data storage library may reduce an amount of resources needed to communicate data to the host system during the creation of the search index. This may improve a performance of the data storage library.

Further still, by transparently loading the data storage cartridge into the data storage drive of the data storage library, the search index creation may be performed at the data storage library without interrupting the use of the data storage library by one or more host systems. This may reduce a wait time for data by the host systems, which may in turn improve a performance of the host systems.

Also, by creating the search index for data stored within the data storage library, searches performed on that data may be improved, utilizing the search index. For example, a time taken to perform a search within the data storage library may be decreased, and the search may be performed more efficiently, which may increase a performance of one or more entities performing the search (e.g., one or more data storage drives, a library controller, a host system, etc.), as well as one or more entities receiving results of the search.

Now referring to FIG. 11, a flowchart of a method 1100 for transparently managing data storage cartridges is shown according to one embodiment. The method 1100 may be performed in accordance with the present invention in any of the environments depicted in FIGS. 1-9 and 12, among others, in various embodiments. Of course, more or less operations than those specifically described in FIG. 11 may be included in method 1100, as would be understood by one of skill in the art upon reading the present descriptions.

Each of the steps of the method 1100 may be performed by any suitable component of the operating environment. For example, in various embodiments, the method 1100 may be partially or entirely performed by one or more servers, computers, or some other device having one or more processors therein. The processor, e.g., processing circuit(s), chip(s), and/or module(s) implemented in hardware and/or software, and preferably having at least one hardware component may be utilized in any device to perform one or more steps of the method 1100. Illustrative processors include, but are not limited to, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., combinations thereof, or any other suitable computing device known in the art.

As shown in FIG. 11, method 1100 may initiate with operation 1102, where a creation of a search index is initiated. Additionally, method 1100 may proceed with operation 1104, where a first data storage cartridge is transparently loaded into a data storage drive within the data storage library. Further, method 1100 may proceed with operation 1106, where creation or update of the search index is initiated utilizing the first data storage cartridge and the data storage drive. In one embodiment, the search index may be created utilizing data stored within the data storage drive. In another embodiment, the search index creation may be performed utilizing a library controller or the data storage drive.

Additionally, method 1100 may proceed with operation 1108, where a request is received to access data on a second data storage cartridge, utilizing the data storage drive. In one embodiment, the request may include a request to load the second data storage cartridge into the data storage drive. In another embodiment, the request may include a specific indication of the data storage drive. For example, the data storage drive may be presented to the host application as empty by the library controller, and the host application may request that the data storage drive be used by the host controller to access data in the second data storage cartridge.

Further, method 1100 may proceed with operation 1110, where the creation of the search index utilizing the first data storage cartridge and the data storage drive is postponed. In one embodiment, the search index creation may be paused or stopped completely before it has completed. In another embodiment, partial results of the search index creation (e.g., a partial search index, etc.) may be saved locally at the library controller. In yet another embodiment, the partial results may be saved to a cloud computing/storage environment.

Further still, method 1100 may proceed with operation 1112, where the first data storage cartridge is transparently removed from the data storage drive. In one embodiment, the first data storage cartridge may be returned to its home slot without informing a host application/host system. In another embodiment, the first data storage cartridge may be returned to another available slot other than its home slot without informing a host application/host system. In yet another embodiment, the request to access data on the second data storage cartridge may be intentionally delayed during the transparent removal of the first data storage cartridge.

Also, method 1100 may proceed with operation 1114, where the second data storage cartridge is loaded into the data storage drive. In one embodiment, the second data storage cartridge may be removed from its home slot and inserted into the data storage drive. In yet another embodiment, the library controller may update inventory data to indicate that the second data storage cartridge is not in its home slot. In still another embodiment, the library controller may update a library map (e.g., element address table, inventory data, etc.) to indicate that the second data storage cartridge is loaded into the data storage drive.

In addition, method 1100 may proceed with operation 1116, where access to the data on the second data storage cartridge is provided, utilizing the data storage drive. In one embodiment, the access may include modifying the data on the second data storage cartridge. For example, the request to access data may include a request sent by a host application to write, modify, or delete data on the second data storage cartridge. In another example, providing access to the data on the second data storage cartridge may include modifying, by the data storage drive, the data on the second data storage cartridge.

Furthermore, in one embodiment, the access may include reading the data on the second data storage cartridge. For example, the request to access data may include a request sent by a host application to read data from the second data storage cartridge. In another example, providing access to the data on the second data storage cartridge may include reading, by the data storage drive, the data on the second data storage cartridge, and providing the data to the library controller.

Further still, in one embodiment, the library controller may return read data from the second data storage cartridge to the host application. In another embodiment, the library controller may send a confirmation of a modification of the data within the second data storage cartridge to the host application.

Also, method 1100 may proceed with operation 1118, where the second data storage cartridge is removed from the data storage drive. In one embodiment, the second data storage cartridge may be removed from the data storage drive in response to a completion of desired access to the data on the second data storage cartridge, or in response to a host request to move the cartridge to its home slot or some other slot in the library. In another embodiment, the second data storage cartridge may be inserted into its home slot or another slot in the library. In yet another embodiment, the library controller may update inventory data to indicate that the second data storage cartridge is in its new location (e.g., its home slot or some other slot in the library). In still another embodiment, the library controller may update a library map (e.g., element address table, inventory data, etc.) to indicate that the data storage drive is empty.

Additionally, method 1100 may proceed with operation 1120, where the first data storage cartridge is transparently reloaded into the data storage drive, or loaded into a second data storage drive. In one embodiment, the first data storage cartridge may be transparently loaded into a data storage drive in response to a determination by the library controller that the data storage drive is empty.

Further, method 1100 may proceed with operation 1122, where the search index creation is resumed utilizing the first data storage cartridge and a data storage drive. In one embodiment, the search index creation may be resumed from the point where it was postponed. For example, the partial results of the search index creation may be retrieved and added to during the resumed search index creation. In another embodiment, a new search index may be initiated utilizing the first data storage cartridge and the data storage drive. For example, the partial results of the search index creation may be discarded and a new search index may be created. Operation 1120 and/or 1122 may be performed at any time after removing the first data storage cartridge from the data storage drive in operation 1112. For example, another empty data storage drive may be utilized to resume the search. Still further, operation 1120 and/or 1122 may be omitted (e.g., if the desired behavior is to stop the search index creation after a conflict for the data storage drive has occurred).

In this way, an effect that the search index creation utilizing the first data storage cartridge has on an availability of the data storage drive may be minimized.

FIG. 12 illustrates an exemplary cartridge search index creation environment 1200, according to one exemplary embodiment. As shown, a host system 1202 is in communication with a data storage library 1204. It should be noted that, although a single host system 1202 is pictured, a plurality of host systems may be in communication with the data storage library 1204 simultaneously.

Additionally, in one embodiment, a host application 1206 running within the host system 1202 may send a search request to a management interface 1216 of the data storage library 1204 over a communications network 1210. In one embodiment, the communications network 1210 may include an ethernet connection, a fiber channel connection, etc. Of course, however, the search request may be received from an entity other than the host system 1202. In another embodiment, in response to receiving the search request, the management interface 1216 may send the search request to the library controller 1208 within the data storage library 1204. In yet another embodiment, in response to receiving the search request, the library controller 1208 may initiate the creation of a search index. Of course, however, the library controller 1208 may initiate the creation of a search index in response to other criteria (e.g., in response to a request to create a search index for predetermined data, in response to a predetermined schedule, in response to data being introduced, modified and/or removed within the data storage library 1204, etc.).

In another embodiment, the library controller 1208 may identify a data storage drive 1214A as open/empty/available from a plurality of data storage drives 1214A-N. In still another embodiment, more than one library controller 1208 may be located within the data storage library 1204.

Further, in one embodiment, in response to initiating the creation of the search index, the library controller 1208 may also select a first data storage cartridge containing data for which the search index is to be created from the data storage cartridge repository 1212. In one embodiment, the first data storage cartridge may be identified within the request to perform the creation of the search index. In another embodiment, the first data storage cartridge may be identified as storing data for which the search index is to be created. In another embodiment, the first data storage cartridge may be identified as storing data for which a search request is being performed and the search index may be created as part of, or in parallel with, that search.

In another embodiment, the library controller 1208 may transparently load the first data storage cartridge into the data storage drive 1214A. In another embodiment, the library controller 1208 may instruct the data storage drive 1214A to create a search index for data stored within the first data storage cartridge. In yet another embodiment, the library controller 1208 may retrieve, from the data storage drive 1214A, data from the first data storage cartridge, and the library controller 1208 may create the search index utilizing the retrieved data.

Further still, in one embodiment, because the library controller 1208 may transparently load the selected cartridge into the data storage drive 1214A, the host application 1206 may view the data storage drive 1214A as open/empty/available, and may send an access request for data on a second data storage cartridge, utilizing the data storage drive 1214A, to the library controller 1208. In response to receiving the access request, the library controller 1208 may determine that the creation of the search index utilizing the first data storage cartridge on the data storage drive 1214A has not completed, and may postpone the creation of the search index utilizing the first data storage cartridge on the data storage drive 1214A as a result.

In another embodiment, a partially created search index may be stored within the first data storage cartridge, within another data storage cartridge different from the first data storage cartridge, within removable media attached to the data storage drive 1214A, within a cloud storage environment, within the library controller 1208, within the host system 1202, within other storage associated with a data storage drive or the library controller 1208, etc.

Also, in one embodiment, the library controller 1208 may then transparently remove the first data storage cartridge from the data storage drive 1214A, and may return the first data storage cartridge to the data storage cartridge repository 1212. Alternatively, the library controller 1208 may transparently remove the first data storage cartridge from the data storage drive 1214A, and may place it in another empty data storage drive (e.g., data storage drive 1214B) in a transparent manner for the purpose of resuming or restarting the search on the first data storage cartridge. The library controller 1208 may then retrieve the second data storage cartridge from the data storage cartridge repository 1212 and may load the second data storage cartridge into the data storage drive 1214A in a non-transparent manner (e.g., such that the host application 1206 now views the data storage drive 1214A as full, etc.). Access to the data on the second data storage cartridge may then be performed utilizing the data storage drive 1214A, according to requests sent by the host application 1206.

In addition, once the access to the data on the second data storage cartridge has completed, the library controller 1208 may then remove the second data storage cartridge from the data storage drive 1214A and may place the second data storage cartridge back in the data storage cartridge repository 1212 in a non-transparent manner (e.g., such that the host application 1206 now views the data storage drive 1214A as empty, etc.). The library controller may then transparently load the first data storage cartridge back into the data storage drive 1214A, and may resume or restart the creation of the search index utilizing data stored on the first data storage cartridge (unless the cartridge had already been loaded into another empty drive as described above).

Furthermore, in one embodiment, when the creation of the search index utilizing data stored on the first data storage cartridge has completed, the library controller may send the search index to the management interface 1216 of the data storage library 1204, and the management interface 1216 may return the search index to the host system 1202 (or any other entity that initiated the search). In another embodiment, the search index may be returned utilizing a different management interface from the management interface 1216 used by the library controller 1208 to receive the search request.

In yet another embodiment, the search index may be stored within the first data storage cartridge, within another data storage cartridge different from the first data storage cartridge, within removable media attached to the data storage drive 1214A, within a cloud storage environment, within the library controller 1208, within the host system 1202, etc.

In this way, a search index may be created at the library controller 1208 and/or the data storage drive 1214A, instead of at the host application 1206 of the host system 1202. This may reduce an amount of processing by the host system 1202, may reduce an amount of necessary transmissions sent by the library controller 1208, and may reduce an amount of bandwidth usage over the communications network 1210.

Some automated data storage libraries provide a feature that verifies the health of the media in the library. For example, an automated data storage library may provide a media verification function where the cartridges are periodically accessed (loaded, threaded, read, and/or written) to confirm that the cartridges and/or the media within the cartridges is still viable. A search index creation or update operation may be used as another mechanism for indicating that the media is viable. For example, as a search index is created utilizing data stored within a data storage cartridge, the data storage cartridge may be flagged as being “verified” for purposes of media verification. Herein, media verification may refer to verification of the cartridge and/or the storage medium associated with the cartridge.

Nondisruptive Cartridge Index Capability in an Automated Data Storage Library

DESCRIPTION

In one embodiment, an automated data storage library may provide nondisruptive index capability of one or more cartridges within the library. For example, an automated data storage library nondisruptively builds a search index for data stored on removable media within the automated data storage library. The index may be built as part of a requested search operation or may be built as an independent operation unrelated to any search request.

Additionally, in one embodiment, in order to make the index operation nondisruptive, cartridges are transparently loaded into data storage drives and the drives perform index operations on the contents of the cartridges. The index operation may be initiated via a user interface of the library (web user interface, operator panel, command line interface, application programming interface, SNMP, etc.). For example, after installing firmware that supports this capability or after bulk loading pre-written data storage cartridges, a user may initiate an index operation from a web user interface of the library.

Further, in one embodiment, the index operation may be initiated when a user requests a search of data in the automated data storage library. For example, when a search operation is imitated, the library may build a search index (or add to an existing search index) as part of the search operation. Still further, the index operation may be initiated automatically by the automated data storage library. For example, the library may perform a periodic index operation based on date/time, based on new media being introduced into the library, based on media being removed from the library, based on media being written or erased, etc.

Further still, in one embodiment, cartridges may be transparently loaded into data storage drives and the drives perform index operations on the contents of the cartridges. The search operation may use a built-in search and/or index capability provided by the drive or it may use individual data access commands to perform the index operation.

Also, in one embodiment, the library may provide the capability to tune index operation parameters. For example, there may be a tradeoff between index performance and storage space used by the index data, there may be compression and/or encryption options, there may be options for how/when data is added to and/or removed from the index, etc.

In addition, in one embodiment, the library may use a data storage drive with removable media to store the index data (e.g., the same drives and media that perform the data search operations). Alternatively, the library may use hard drives, USB flash drives, solid state drives, tape drives, optical drives, or any other data storage device that is capable of holding search index results.

Furthermore, in one embodiment, the following may be implemented to make the index operation transparent and nondisruptive:

-   -   The library may wait for an empty drive and then load a         cartridge to be searched/indexed into the drive.     -   There may be utility drives that are not associated with         application drives.     -   The library may instruct the drive to report to host         applications as being empty.     -   The library may report inventory data (e.g., an element address         table, a library map, etc.) showing the cartridge located in its         home slot.

Further still, in one embodiment, if the library removable media drives are used to store the index data, the following may be implemented to make storage of the index data transparent and nondisruptive:

-   -   The library may wait for an empty drive and then load a         cartridge that holds the index data. Other storage devices         within the library may be used to temporarily hold the data         until a drive becomes available.     -   There may be utility drives that are not associated with         application drives.     -   The library may instruct the drive to report to host         applications as being empty.     -   The library may report inventory data (e.g., an element address         table, a library map, etc.) showing the cartridge located in its         home slot.

Also, in one embodiment, the library may support media verification which is used to confirm that media is accessible and readable. Media verification could be combined with this idea. For example, a media verification operation on a particular cartridge could perform an index operation in addition to, or in lieu of, the media verification operation. In another example, an index operation on a particular cartridge may count as a verification operation of that same cartridge.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein includes an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which includes one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

Moreover, a system according to various embodiments may include a processor and logic integrated with and/or executable by the processor, the logic being configured to perform one or more of the process steps recited herein. By integrated with, what is meant is that the processor has logic embedded therewith as hardware logic, such as an application specific integrated circuit (ASIC), a FPGA, etc. By executable by the processor, what is meant is that the logic is hardware logic; software logic such as firmware, part of an operating system, part of an application program; etc., or some combination of hardware and software logic that is accessible by the processor and configured to cause the processor to perform some functionality upon execution by the processor. Software logic may be stored on local and/or remote memory of any memory type, as known in the art. Any processor known in the art may be used, such as a software processor module and/or a hardware processor such as an ASIC, a FPGA, a central processing unit (CPU), an integrated circuit (IC), a graphics processing unit (GPU), etc.

A data processing system suitable for storing and/or executing program code may include at least one processor, which may be or be part of a controller, coupled directly or indirectly to memory elements through a system bus, such as processor 400 of FIG. 4. The memory elements can include local memory employed during actual execution of the program code, such as nonvolatile memory 404 of FIG. 4, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

It will be clear that the various features of the foregoing systems and/or methodologies may be combined in any way, creating a plurality of combinations from the descriptions presented above.

It will be further appreciated that embodiments of the present invention may be provided in the form of a service deployed on behalf of a customer to offer service on demand.

While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. 

What is claimed is:
 1. A computer-implemented method, comprising: in response to an initiation of a creation of a search index for a data storage cartridge, loading the data storage cartridge into a data storage drive of a data storage library; providing an indication to an application that the data storage cartridge is located in a storage slot while the data storage drive is loaded with the data storage cartridge, where providing the indication conceals from the application that the data storage drive is loaded with the data storage cartridge for use in creating the search index; creating the search index, utilizing the data storage cartridge and the data storage drive; and storing the search index.
 2. The computer-implemented method of claim 1, wherein the initiating of the creation of the search index is performed in response to a receipt of a search request.
 3. The computer-implemented method of claim 1, comprising: reporting the data storage drive as being empty when the data storage drive is loaded with the data storage cartridge.
 4. The computer-implemented method of claim 1, wherein the initiating of the creation of the search index is performed in response to new data being introduced into the data storage library.
 5. The computer-implemented method of claim 1, comprising: identifying a host application drive that is not currently being used within the data storage library; loading the data storage cartridge into the host application drive; and presenting the data storage cartridge as being located in the storage slot when the data storage cartridge is loaded into the host application drive.
 6. The computer-implemented method of claim 1, comprising: identifying the data storage drive as not currently being used within the data storage library; and loading the data storage cartridge into the data storage drive of the data storage library.
 7. The computer-implemented method of claim 1, wherein the indication that the data storage cartridge is located in the storage slot is provided to the application in response to receiving a request for inventory data from the application.
 8. The computer-implemented method of claim 1, wherein the creating of the search index includes parsing data stored within the data storage cartridge by the data storage drive, and creating one or more index data structures by the data storage drive, based on the parsed data.
 9. The computer-implemented method of claim 1, wherein all or part of the search index is stored within the data storage cartridge.
 10. The computer-implemented method of claim 1, wherein: the creation of the search index is initiated automatically according to a predetermined schedule, and all or part of the search index is stored within another data storage cartridge.
 11. The computer-implemented method of claim 1, wherein all or part of the search index is stored within media other than the data storage cartridge.
 12. The computer-implemented method of claim 1, comprising flagging the data storage cartridge as being verified.
 13. A computer program product comprising one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions comprising instructions configured to cause one or more processors to perform a method comprising: in response to an initiation of a creation of a search index for a data storage cartridge, loading, utilizing the one or more processors, the data storage cartridge into a data storage drive of a data storage library; providing, utilizing the one or more processors, an indication to an application that the data storage cartridge is located in a storage slot while the data storage drive is loaded with the data storage cartridge, where providing the indication conceals from the application that the data storage drive is loaded with the data storage cartridge for use in creating the search index; creating, utilizing the one or more processors, the search index, utilizing the data storage cartridge and the data storage drive; and storing, utilizing the one or more processors, the search index.
 14. The computer program product of claim 13, comprising reporting the data storage drive as being empty when the data storage drive is loaded with the data storage cartridge, utilizing the one or more processors.
 15. A library controller, comprising: a processor; and logic integrated with the processor, executable by the processor, or integrated with and executable by the processor, the logic being configured to: in response to an initiation of a creation of a search index for a data storage cartridge, load the data storage cartridge into a data storage drive of a data storage library; provide an indication to an application that the data storage cartridge is located in a storage slot while the data storage drive is loaded with the data storage cartridge, where providing the indication conceals from the application that the data storage drive is loaded with the data storage cartridge for use in creating the search index; create the search index, utilizing the data storage cartridge and the data storage drive; and store the search index.
 16. A computer-implemented method, comprising: initiating a creation of a search index; transparently loading a first data storage cartridge into a data storage drive within a data storage library; initiating a creation of the search index utilizing the first data storage cartridge and the data storage drive; receiving a request to access data on a second data storage cartridge, utilizing the data storage drive; postponing the creation of the search index utilizing the first data storage cartridge and the data storage drive; removing the first data storage cartridge from the data storage drive; loading the second data storage cartridge into the data storage drive; and providing access to the data on the second data storage cartridge, utilizing the data storage drive.
 17. The computer-implemented method of claim 16, wherein removing the first data storage cartridge from the data storage drive further comprises: transparently loading the first data storage cartridge into a second data storage drive; and: resuming the creation of the search index utilizing the first data storage cartridge and the second data storage drive, or restarting the creation of the search index utilizing the first data storage cartridge and the second data storage drive.
 18. The computer-implemented method of claim 16, wherein loading the second data storage cartridge includes: removing the second data storage cartridge from its home slot; inserting the second data storage cartridge into the data storage drive; updating inventory data to indicate that the second data storage cartridge is not in its home slot; and updating a library map to indicate that the second data storage cartridge is loaded into the data storage drive.
 19. The computer-implemented method of claim 16, further comprising: removing the second data storage cartridge from the data storage drive; transparently reloading the first data storage cartridge into the data storage drive; and resuming the creation of the search index utilizing the first data storage cartridge and the data storage drive.
 20. The computer-implemented method of claim 19, wherein the creation of the search index utilizing the first data storage cartridge and the data storage drive is resumed from a point where it was postponed.
 21. The computer-implemented method of claim 19, wherein resuming the creation of the search index utilizing the first data storage cartridge and the data storage drive includes initiating a creation of a new search index utilizing the first data storage cartridge and the data storage drive.
 22. A computer-implemented method, comprising: automatically initiating a creation of a search index for a data storage cartridge according to a schedule; transparently loading the data storage cartridge into a data storage drive of a data storage library, including: identifying a data storage drive that is not currently being used within the data storage library, loading the data storage cartridge into the data storage drive, reporting the data storage drive as being empty when the data storage cartridge is loaded into the data storage drive, receiving a request from a host application for inventory data, and in response to receiving the request, providing inventory data to the host application indicating that the data storage cartridge is in a storage slot, and not in the data storage drive while the data storage cartridge is loaded into the data storage drive; creating the search index, utilizing the data storage cartridge and the data storage drive, where all or part of the search index is stored within another data storage cartridge; and saving the search index.
 23. The method of claim 22, wherein reporting the data storage drive as being empty comprises: receiving, from a host application, a request for a library map, and providing to the host application the library map, where the library map indicates that the data storage drive is empty.
 24. The method of claim 22, wherein creating the search index includes parsing data stored within the data storage cartridge by the data storage drive, and creating one or more index data structures, based on the data. 